Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee4d55b555ca3ab89b9d3baf590daa948fa54e74bf5c321dbd6497f7a8b3aa7e

Tx prefix hash: 36fee85e42a519d456895d3ad15d34e771c334899aec09c2b8f201495f9c13cb
Tx public key: a3ecf66d8ef4f15be48985bfe04b643190317ec6045ef06e0adbd2b09b0fc076
Timestamp: 1709954324 Timestamp [UCT]: 2024-03-09 03:18:44 Age [y:d:h:m:s]: 00:316:11:16:08
Block: 974279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226487 RingCT/type: yes/0
Extra: 01a3ecf66d8ef4f15be48985bfe04b643190317ec6045ef06e0adbd2b09b0fc0760211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f536865983f3a4bd593eb3c1aac267c7e35a6628b8a7f87185c8f12f3a5069e 0.600000000000 1434234 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": 974289, "vin": [ { "gen": { "height": 974279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f536865983f3a4bd593eb3c1aac267c7e35a6628b8a7f87185c8f12f3a5069e" } } ], "extra": [ 1, 163, 236, 246, 109, 142, 244, 241, 91, 228, 137, 133, 191, 224, 75, 100, 49, 144, 49, 126, 198, 4, 94, 240, 110, 10, 219, 210, 176, 155, 15, 192, 118, 2, 17, 0, 0, 0, 1, 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