Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab07da39070c604a8dc6d3e16d14cfb74811e7ddae82e2342146d481f5d9fc23

Tx prefix hash: 857b31057a41db7cb02c676786eb0d3b10e83eae2862580b53740b471d01a936
Tx public key: ddb0bf50fd9014b64eb3c3b952c11de09bbbcd21c21fdf76056509e811579dcc
Timestamp: 1728449136 Timestamp [UCT]: 2024-10-09 04:45:36 Age [y:d:h:m:s]: 01:031:11:33:11
Block: 1127603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280880 RingCT/type: yes/0
Extra: 01ddb0bf50fd9014b64eb3c3b952c11de09bbbcd21c21fdf76056509e811579dcc021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 057a3618ad67ecb9cf5d6bd8e01b1f3c6a2164dfea805cd634fbadb7a3aa65c8 0.600000000000 1610410 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": 1127613, "vin": [ { "gen": { "height": 1127603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "057a3618ad67ecb9cf5d6bd8e01b1f3c6a2164dfea805cd634fbadb7a3aa65c8" } } ], "extra": [ 1, 221, 176, 191, 80, 253, 144, 20, 182, 78, 179, 195, 185, 82, 193, 29, 224, 155, 187, 205, 33, 194, 31, 223, 118, 5, 101, 9, 232, 17, 87, 157, 204, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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