Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e4645a92da16ea4b177993536623c6802f4201ac45eed76341243ea2af7a0b

Tx prefix hash: a966b79b404cf30dc43e8a209f87fe978e9645e9e36b49948fa8519b9d79f389
Tx public key: 67b1b67cef9cc56f55aeb4f6f5726f4da81dbf80b8a536d3106a1922e91c75d5
Timestamp: 1744766629 Timestamp [UCT]: 2025-04-16 01:23:49 Age [y:d:h:m:s]: 00:219:13:40:54
Block: 1262385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154635 RingCT/type: yes/0
Extra: 0167b1b67cef9cc56f55aeb4f6f5726f4da81dbf80b8a536d3106a1922e91c75d5021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04c0fc0b5bd39eae12c5e374b442eca67af2efefbdc881af5da0f1c5a138381b 0.600000000000 1749564 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": 1262395, "vin": [ { "gen": { "height": 1262385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04c0fc0b5bd39eae12c5e374b442eca67af2efefbdc881af5da0f1c5a138381b" } } ], "extra": [ 1, 103, 177, 182, 124, 239, 156, 197, 111, 85, 174, 180, 246, 245, 114, 111, 77, 168, 29, 191, 128, 184, 165, 54, 211, 16, 106, 25, 34, 233, 28, 117, 213, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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