Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55137c4ecbd2953d18a59219c8927a7444d5bd1606ccf1ce3912453af8cad073

Tx prefix hash: 1d1970552cdd1afdb647c08b7da1b3f2b3a2328b7b5f2b2f97731b3d6c982d38
Tx public key: 0d65f665737b34ceeab7f569dca12ed4ecbd981c50fd2b68e3cd3a41b89cbfc2
Timestamp: 1729468911 Timestamp [UCT]: 2024-10-21 00:01:51 Age [y:d:h:m:s]: 01:043:07:36:41
Block: 1136030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289378 RingCT/type: yes/0
Extra: 010d65f665737b34ceeab7f569dca12ed4ecbd981c50fd2b68e3cd3a41b89cbfc20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d0a4567dec1a28c52bd82976c77c2239ecd4de3610ac275dfad4f7a2632266a 0.600000000000 1619371 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": 1136040, "vin": [ { "gen": { "height": 1136030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d0a4567dec1a28c52bd82976c77c2239ecd4de3610ac275dfad4f7a2632266a" } } ], "extra": [ 1, 13, 101, 246, 101, 115, 123, 52, 206, 234, 183, 245, 105, 220, 161, 46, 212, 236, 189, 152, 28, 80, 253, 43, 104, 227, 205, 58, 65, 184, 156, 191, 194, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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