Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c2ee26de4f1ba7cd070d9074b930537909e4d65a7a867f5f47d768dbbf61485

Tx prefix hash: 7a415fabe1973d27b0df0e54158707b269ac2c45c997ec761d41f15971f22ec6
Tx public key: 7d6cfde87439b070276d780b9c0eb9dc49bda102b93e9b4fe30f23f27d76a239
Timestamp: 1736089721 Timestamp [UCT]: 2025-01-05 15:08:41 Age [y:d:h:m:s]: 00:163:01:00:43
Block: 1190819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116235 RingCT/type: yes/0
Extra: 017d6cfde87439b070276d780b9c0eb9dc49bda102b93e9b4fe30f23f27d76a23902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1d8acd7f4da493f8eaff0e297c9c82a49ab9aaad07012a85cfda7e95d992fab 0.600000000000 1677338 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": 1190829, "vin": [ { "gen": { "height": 1190819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1d8acd7f4da493f8eaff0e297c9c82a49ab9aaad07012a85cfda7e95d992fab" } } ], "extra": [ 1, 125, 108, 253, 232, 116, 57, 176, 112, 39, 109, 120, 11, 156, 14, 185, 220, 73, 189, 161, 2, 185, 62, 155, 79, 227, 15, 35, 242, 125, 118, 162, 57, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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