Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e38d5839fac27c03d0808efc9e9f8af0e6ce9c1120603da5782cc7a11063020

Tx prefix hash: a91ec0229bfe01b19c070dc4c1f4cefd78f2ef6919664e3d394b7a85d42a914c
Tx public key: 1d59b13a99813c61945e6e029044676092f3b4f2cd5e42bddd3290068d449a74
Timestamp: 1702600179 Timestamp [UCT]: 2023-12-15 00:29:39 Age [y:d:h:m:s]: 01:159:06:51:09
Block: 913291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375024 RingCT/type: yes/0
Extra: 011d59b13a99813c61945e6e029044676092f3b4f2cd5e42bddd3290068d449a7402110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bfc8d1aa04fdc4decd99b83adf492d1f91b3ef747491577e3b9aac94a4f9ca1 0.600000000000 1370557 of 15

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": 913301, "vin": [ { "gen": { "height": 913291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bfc8d1aa04fdc4decd99b83adf492d1f91b3ef747491577e3b9aac94a4f9ca1" } } ], "extra": [ 1, 29, 89, 177, 58, 153, 129, 60, 97, 148, 94, 110, 2, 144, 68, 103, 96, 146, 243, 180, 242, 205, 94, 66, 189, 221, 50, 144, 6, 141, 68, 154, 116, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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