Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3900d585496c0b050e8ffd967d58efa6e2336dc5044a89d792bb38194bd19e89

Tx prefix hash: 1a0851b60eca8c147e1395dc4b599bff96c8cca49d9dc0b0e320856eea51b563
Tx public key: 74479b55fd8c7cf69b7dadecb0527631bdb040a0e83fcd9b4b4fc6bb49f304f7
Timestamp: 1723193886 Timestamp [UCT]: 2024-08-09 08:58:06 Age [y:d:h:m:s]: 00:273:02:34:07
Block: 1084034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195094 RingCT/type: yes/0
Extra: 0174479b55fd8c7cf69b7dadecb0527631bdb040a0e83fcd9b4b4fc6bb49f304f702110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19215cf900842cc88a35292e0ef96fd93ea93a5803e1bce16765f3e6757dc02b 0.600000000000 1558163 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": 1084044, "vin": [ { "gen": { "height": 1084034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19215cf900842cc88a35292e0ef96fd93ea93a5803e1bce16765f3e6757dc02b" } } ], "extra": [ 1, 116, 71, 155, 85, 253, 140, 124, 246, 155, 125, 173, 236, 176, 82, 118, 49, 189, 176, 64, 160, 232, 63, 205, 155, 75, 79, 198, 187, 73, 243, 4, 247, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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