Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd065068cd736b8c9627df1809be40f27fde2e6df04b274d7d686689368f0da9

Tx prefix hash: 2f2aa24ba7dd1ae05320d2314fff68d3b836eb1d2accc853d216cd2b4eb97338
Tx public key: 11117f31945487ab5fbe7de9b7c6224c6e3d85397154c246971d5738fd80b84d
Timestamp: 1728867683 Timestamp [UCT]: 2024-10-14 01:01:23 Age [y:d:h:m:s]: 00:212:18:59:45
Block: 1131080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151890 RingCT/type: yes/0
Extra: 0111117f31945487ab5fbe7de9b7c6224c6e3d85397154c246971d5738fd80b84d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b6c9f56846e84d5b33eefde628e72286a6c64b11a35b059f09803f3343a51d7 0.600000000000 1613961 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": 1131090, "vin": [ { "gen": { "height": 1131080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b6c9f56846e84d5b33eefde628e72286a6c64b11a35b059f09803f3343a51d7" } } ], "extra": [ 1, 17, 17, 127, 49, 148, 84, 135, 171, 95, 190, 125, 233, 183, 198, 34, 76, 110, 61, 133, 57, 113, 84, 194, 70, 151, 29, 87, 56, 253, 128, 184, 77, 2, 17, 0, 0, 0, 1, 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