Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdfb4037481a70f0bf550ea3f7d55ca0b3650d3cb05b1e439a82001ce92b747b

Tx prefix hash: 2e6b15c0ea139acf181eba6680937f0db3a128ebc58da2e7bbdd2284381e7e5d
Tx public key: c18a72dbf6e5daba69d588b72268e010d328a44f556cfb91247d655ebd3c2e32
Timestamp: 1665711771 Timestamp [UCT]: 2022-10-14 01:42:51 Age [y:d:h:m:s]: 02:135:16:20:04
Block: 608539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 618559 RingCT/type: yes/0
Extra: 01c18a72dbf6e5daba69d588b72268e010d328a44f556cfb91247d655ebd3c2e3202110000000133af99f4000000000000000000

1 output(s) for total of 5.910955961000 dcy

stealth address amount amount idx
00: b2c5fe568bddaa82835e356522dc94fb7f84feae5b30cbd3160957573b87c8e1 5.910955961000 1045244 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": 608549, "vin": [ { "gen": { "height": 608539 } } ], "vout": [ { "amount": 5910955961, "target": { "key": "b2c5fe568bddaa82835e356522dc94fb7f84feae5b30cbd3160957573b87c8e1" } } ], "extra": [ 1, 193, 138, 114, 219, 246, 229, 218, 186, 105, 213, 136, 183, 34, 104, 224, 16, 211, 40, 164, 79, 85, 108, 251, 145, 36, 125, 101, 94, 189, 60, 46, 50, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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