Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0b8be786a93bd57cf59e23f64fe459663795e66d5dfdc0f91bd92762afb051f

Tx prefix hash: 39065257366ea66e96ae78e15d8dc5f30f19246a1c76867f7dd83501ab2217b1
Tx public key: a6d5087b37f1c20aaf642958cc900b6eaa9844dc0bf7ec66dabd47a106ee8942
Timestamp: 1635990172 Timestamp [UCT]: 2021-11-04 01:42:52 Age [y:d:h:m:s]: 03:362:10:09:49
Block: 366848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1035062 RingCT/type: yes/0
Extra: 01a6d5087b37f1c20aaf642958cc900b6eaa9844dc0bf7ec66dabd47a106ee8942021100000001a272b9cb000000000000000000

1 output(s) for total of 37.367001003000 dcy

stealth address amount amount idx
00: 24c805902870689d7df9b23c345d15d422f28cc8f78ceeaf1286ffc7755c07c9 37.367001003000 744544 of 0

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": 366858, "vin": [ { "gen": { "height": 366848 } } ], "vout": [ { "amount": 37367001003, "target": { "key": "24c805902870689d7df9b23c345d15d422f28cc8f78ceeaf1286ffc7755c07c9" } } ], "extra": [ 1, 166, 213, 8, 123, 55, 241, 194, 10, 175, 100, 41, 88, 204, 144, 11, 110, 170, 152, 68, 220, 11, 247, 236, 102, 218, 189, 71, 161, 6, 238, 137, 66, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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