Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 334584ef4dbe13e199577f1c6f3f0bfedc30d6fdfad5bdbc32a50b69fc5f2a8c

Tx prefix hash: 8475e9b327cefb0aa2b7f235522af9a4f66c0b5809634e29ec0817dbe8b5260f
Tx public key: ba0a0417af52581e56867fb1d6f7eaeea4ad07c0f89f98ea2c1e507e9a54634e
Timestamp: 1725065866 Timestamp [UCT]: 2024-08-31 00:57:46 Age [y:d:h:m:s]: 00:227:01:49:01
Block: 1099554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162145 RingCT/type: yes/0
Extra: 01ba0a0417af52581e56867fb1d6f7eaeea4ad07c0f89f98ea2c1e507e9a54634e021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f157b86d86cdb27118f13caa14315b1ff68bf3da2a7d025033d0b351bd434212 0.600000000000 1575517 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": 1099564, "vin": [ { "gen": { "height": 1099554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f157b86d86cdb27118f13caa14315b1ff68bf3da2a7d025033d0b351bd434212" } } ], "extra": [ 1, 186, 10, 4, 23, 175, 82, 88, 30, 86, 134, 127, 177, 214, 247, 234, 238, 164, 173, 7, 192, 248, 159, 152, 234, 44, 30, 80, 126, 154, 84, 99, 78, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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