Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbc563b007cf2c8f30dec5574a3eceacc9bc6bded5a6b83d7ef1ba624bfd6f78

Tx prefix hash: bc61af761cce889364b41fd88e5221d7d5fc45694a762b565e25e7287f68c026
Tx public key: 43d1b0b4b8cb1c39bf7782a685ec4a94ece9b69fd3788fa6a7825b2fc1ec4e06
Timestamp: 1699708667 Timestamp [UCT]: 2023-11-11 13:17:47 Age [y:d:h:m:s]: 01:104:20:13:34
Block: 889334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336073 RingCT/type: yes/0
Extra: 0143d1b0b4b8cb1c39bf7782a685ec4a94ece9b69fd3788fa6a7825b2fc1ec4e06021100000005faf35c9c000000000000000000

1 output(s) for total of 0.693852691000 dcy

stealth address amount amount idx
00: 015c68ac2dde288239cfaeb441f3189840a398759e1a0f64e939a1dbc4f0677e 0.693852691000 1345325 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": 889344, "vin": [ { "gen": { "height": 889334 } } ], "vout": [ { "amount": 693852691, "target": { "key": "015c68ac2dde288239cfaeb441f3189840a398759e1a0f64e939a1dbc4f0677e" } } ], "extra": [ 1, 67, 209, 176, 180, 184, 203, 28, 57, 191, 119, 130, 166, 133, 236, 74, 148, 236, 233, 182, 159, 211, 120, 143, 166, 167, 130, 91, 47, 193, 236, 78, 6, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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