Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 567ae1b6d2c9526a70863eca5f88bd2671103505fa4c2307b30256ae6d72d631

Tx prefix hash: bd30aabbcb4f89b312a99587aea08d2446c641006821685876fd1920286b35a5
Tx public key: f1255cdf57eb2d16afc1664168cceb50d4e323a559148ad71ab673d1b7c99409
Timestamp: 1577845430 Timestamp [UCT]: 2020-01-01 02:23:50 Age [y:d:h:m:s]: 05:063:02:10:57
Block: 36101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194890 RingCT/type: yes/0
Extra: 01f1255cdf57eb2d16afc1664168cceb50d4e323a559148ad71ab673d1b7c9940902110000004b4ac5aa02000000000000000000

1 output(s) for total of 465.997143046000 dcy

stealth address amount amount idx
00: 5cc80abe7fe125c094d379956a700f74a6e5704c00ae6f7013edae18aa3b92e7 465.997143046000 61045 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 36111, "vin": [ { "gen": { "height": 36101 } } ], "vout": [ { "amount": 465997143046, "target": { "key": "5cc80abe7fe125c094d379956a700f74a6e5704c00ae6f7013edae18aa3b92e7" } } ], "extra": [ 1, 241, 37, 92, 223, 87, 235, 45, 22, 175, 193, 102, 65, 104, 204, 235, 80, 212, 227, 35, 165, 89, 20, 138, 215, 26, 182, 115, 209, 183, 201, 148, 9, 2, 17, 0, 0, 0, 75, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8