Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d693d73090f9f533759146bba6e58045e2df4d48b2ed0f90d914f32bce75e3

Tx prefix hash: 0f6fd88dc0b6aaf1dbe77431673d1c1dbb9bdb7664f45675c89fd54c0691a0cd
Tx public key: cb50fe1d015754e5ab8ce48af7baf7f259411c954080dfd60e81f52dc530c32b
Timestamp: 1694938094 Timestamp [UCT]: 2023-09-17 08:08:14 Age [y:d:h:m:s]: 01:166:09:16:03
Block: 849968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379980 RingCT/type: yes/0
Extra: 01cb50fe1d015754e5ab8ce48af7baf7f259411c954080dfd60e81f52dc530c32b021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.936921563000 dcy

stealth address amount amount idx
00: 17aee15a1447993ee5d3e876192f59cfb6803c65c65c99a997c8481aaad016c6 0.936921563000 1303658 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": 849978, "vin": [ { "gen": { "height": 849968 } } ], "vout": [ { "amount": 936921563, "target": { "key": "17aee15a1447993ee5d3e876192f59cfb6803c65c65c99a997c8481aaad016c6" } } ], "extra": [ 1, 203, 80, 254, 29, 1, 87, 84, 229, 171, 140, 228, 138, 247, 186, 247, 242, 89, 65, 28, 149, 64, 128, 223, 214, 14, 129, 245, 45, 197, 48, 195, 43, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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