Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d15f5d4edcbd4674a3d7ccc770e1dfdb1b2816852252d49fb34f8bb376ad5495

Tx prefix hash: e29230357df6bc6e8579549c9660346c89314f84325f6f2924b05f1300b4a6f1
Tx public key: 68387fb8c75e4e299b2f36a3c5d3758fe969607c1b8abfdc1b2807508bcf5641
Timestamp: 1578071023 Timestamp [UCT]: 2020-01-03 17:03:43 Age [y:d:h:m:s]: 05:130:18:49:29
Block: 37847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1243439 RingCT/type: yes/0
Extra: 0168387fb8c75e4e299b2f36a3c5d3758fe969607c1b8abfdc1b2807508bcf564102110000009a31ef32d6000000000000000000

1 output(s) for total of 459.830769608000 dcy

stealth address amount amount idx
00: a6c9a6f73c0ef688393883438624195d387bf05d0b8f06dfa8d34ddd0860fd06 459.830769608000 64356 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": 37857, "vin": [ { "gen": { "height": 37847 } } ], "vout": [ { "amount": 459830769608, "target": { "key": "a6c9a6f73c0ef688393883438624195d387bf05d0b8f06dfa8d34ddd0860fd06" } } ], "extra": [ 1, 104, 56, 127, 184, 199, 94, 78, 41, 155, 47, 54, 163, 197, 211, 117, 143, 233, 105, 96, 124, 27, 138, 191, 220, 27, 40, 7, 80, 139, 207, 86, 65, 2, 17, 0, 0, 0, 154, 49, 239, 50, 214, 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