Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad73bbc6561fb866a9f97d5005764b5765d6b68450b1b03075fa9c42c57ce431

Tx prefix hash: 91a0f21e30053fbd9acb043d5322f1a2af21a8b5c6bc3177362bd1e5e899637a
Tx public key: 611af1a72e5f7e503f0c2287f4cc8a92317066e9ace48c0365214d3bc7e702f6
Timestamp: 1704804017 Timestamp [UCT]: 2024-01-09 12:40:17 Age [y:d:h:m:s]: 01:157:22:33:43
Block: 931560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373935 RingCT/type: yes/0
Extra: 01611af1a72e5f7e503f0c2287f4cc8a92317066e9ace48c0365214d3bc7e702f60211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 214b7bf2e47b8a152c8b5317d5f233e1ba397107d482e7889ed0352784e72085 0.600000000000 1389462 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": 931570, "vin": [ { "gen": { "height": 931560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "214b7bf2e47b8a152c8b5317d5f233e1ba397107d482e7889ed0352784e72085" } } ], "extra": [ 1, 97, 26, 241, 167, 46, 95, 126, 80, 63, 12, 34, 135, 244, 204, 138, 146, 49, 112, 102, 233, 172, 228, 140, 3, 101, 33, 77, 59, 199, 231, 2, 246, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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