Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a80f713240fd8173e994de459ad2d0d0b7922dcb50323fa557813906800de93

Tx prefix hash: cc46dd64a088e0394db440f75874a28529016e1df94c389789a564aa9c2b1219
Tx public key: 789c6fe8c4a6e3c1f8ad63d23c2f9859750074412726e3690863b37fb79af251
Timestamp: 1633548396 Timestamp [UCT]: 2021-10-06 19:26:36 Age [y:d:h:m:s]: 04:048:11:35:56
Block: 348057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1070170 RingCT/type: yes/0
Extra: 01789c6fe8c4a6e3c1f8ad63d23c2f9859750074412726e3690863b37fb79af2510211000000015d7cc334000000000000000000

1 output(s) for total of 43.127609351000 dcy

stealth address amount amount idx
00: 63069cfd0e35c8031214cfd66e720e40dc7de279e3f37a8b3e9f0635e3240d8c 43.127609351000 712939 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": 348067, "vin": [ { "gen": { "height": 348057 } } ], "vout": [ { "amount": 43127609351, "target": { "key": "63069cfd0e35c8031214cfd66e720e40dc7de279e3f37a8b3e9f0635e3240d8c" } } ], "extra": [ 1, 120, 156, 111, 232, 196, 166, 227, 193, 248, 173, 99, 210, 60, 47, 152, 89, 117, 0, 116, 65, 39, 38, 227, 105, 8, 99, 179, 127, 183, 154, 242, 81, 2, 17, 0, 0, 0, 1, 93, 124, 195, 52, 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