Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9947136d54f1c9217a15d1e664e9fe8417c71647ca88a07765c2c44933ca80ea

Tx prefix hash: 0e6105679e5fcd0785d1e476bc34ca7375ef823933778edfdecad0466089da6d
Tx public key: b1d6c37b57fdf6e62862ade63a4ad0ff30a4f335331193a326b00236bbb1b3cc
Timestamp: 1733216926 Timestamp [UCT]: 2024-12-03 09:08:46 Age [y:d:h:m:s]: 00:025:01:37:05
Block: 1167028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17932 RingCT/type: yes/0
Extra: 01b1d6c37b57fdf6e62862ade63a4ad0ff30a4f335331193a326b00236bbb1b3cc021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4bb83f83d1dfd7dfffc71e75620c5d41ecd9e98b94a7e590e030d872f0ffe88 0.600000000000 1652721 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": 1167038, "vin": [ { "gen": { "height": 1167028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4bb83f83d1dfd7dfffc71e75620c5d41ecd9e98b94a7e590e030d872f0ffe88" } } ], "extra": [ 1, 177, 214, 195, 123, 87, 253, 246, 230, 40, 98, 173, 230, 58, 74, 208, 255, 48, 164, 243, 53, 51, 17, 147, 163, 38, 176, 2, 54, 187, 177, 179, 204, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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