Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb0e91a5ccf700517b0df868786bd62bdc76b1b73b8996a611969e51cd4de157

Tx prefix hash: 24da1196b40b4bc1fbcc358da93b3f2b3f8d31e3fb694614d421d804d7e208d9
Tx public key: 1a1eafc7e98ac52822ef351a102df6611439102bda81094e2ca948799e211a10
Timestamp: 1673435378 Timestamp [UCT]: 2023-01-11 11:09:38 Age [y:d:h:m:s]: 02:301:14:55:08
Block: 672373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 734963 RingCT/type: yes/0
Extra: 011a1eafc7e98ac52822ef351a102df6611439102bda81094e2ca948799e211a100211000000038b7b6602000000000000000000

1 output(s) for total of 3.632027176000 dcy

stealth address amount amount idx
00: a99957b30746965c77f9248ca2116bc868974ce58e3158dacab2eb2f7214baa5 3.632027176000 1113908 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": 672383, "vin": [ { "gen": { "height": 672373 } } ], "vout": [ { "amount": 3632027176, "target": { "key": "a99957b30746965c77f9248ca2116bc868974ce58e3158dacab2eb2f7214baa5" } } ], "extra": [ 1, 26, 30, 175, 199, 233, 138, 197, 40, 34, 239, 53, 26, 16, 45, 246, 97, 20, 57, 16, 43, 218, 129, 9, 78, 44, 169, 72, 121, 158, 33, 26, 16, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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