Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd7d9e7ae1ad147ef5c0c0af8092c5d846fd4ed262713d2a81eae471a09e9b16

Tx prefix hash: 837b72dbfd00852ce75c3648a9dc2e33106b4feb1914fc9dbc536c486e0a5fa0
Tx public key: d073ff17d6bf1114f93e9a2fffccc2d4807dc67d359421760a44c95e4d685635
Timestamp: 1705742080 Timestamp [UCT]: 2024-01-20 09:14:40 Age [y:d:h:m:s]: 01:292:01:44:30
Block: 939315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467570 RingCT/type: yes/0
Extra: 01d073ff17d6bf1114f93e9a2fffccc2d4807dc67d359421760a44c95e4d68563502110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 640ab536c76cab0e4a6610981cc6329b84921175a21b2e5aca95f7b055d36207 0.600000000000 1397409 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": 939325, "vin": [ { "gen": { "height": 939315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "640ab536c76cab0e4a6610981cc6329b84921175a21b2e5aca95f7b055d36207" } } ], "extra": [ 1, 208, 115, 255, 23, 214, 191, 17, 20, 249, 62, 154, 47, 255, 204, 194, 212, 128, 125, 198, 125, 53, 148, 33, 118, 10, 68, 201, 94, 77, 104, 86, 53, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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