Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a35639749c5a437977073b4aff86f196eea2fd9f317cf13689047338022b292

Tx prefix hash: 17ce0bb684f79c02b631fcda54ef95d73615f485d43691e367a2867ab54ddd01
Tx public key: c81b6f03c67cb4db438d8aadb7be5122432e7a31801bd52d026b63d0ed0f5f93
Timestamp: 1705184283 Timestamp [UCT]: 2024-01-13 22:18:03 Age [y:d:h:m:s]: 01:124:19:29:14
Block: 934712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350330 RingCT/type: yes/0
Extra: 01c81b6f03c67cb4db438d8aadb7be5122432e7a31801bd52d026b63d0ed0f5f930211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f68954a9eacf748016404ec6958d5f8a7e8df2646e5f54ba005a41c183b43cf7 0.600000000000 1392728 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": 934722, "vin": [ { "gen": { "height": 934712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f68954a9eacf748016404ec6958d5f8a7e8df2646e5f54ba005a41c183b43cf7" } } ], "extra": [ 1, 200, 27, 111, 3, 198, 124, 180, 219, 67, 141, 138, 173, 183, 190, 81, 34, 67, 46, 122, 49, 128, 27, 213, 45, 2, 107, 99, 208, 237, 15, 95, 147, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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