Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32ce627df643bd7aee074302b2731c43f3955886ee97e06271d48f06ee3a9b91

Tx prefix hash: ef46087380b34f82f69828f7c29d9a9528309811323c0d6b2e814c56b63f685a
Tx public key: 107ce9da6be2c9a57be1a5b856a1634c8007aa7c93b802a47267aa98844c3464
Timestamp: 1728675459 Timestamp [UCT]: 2024-10-11 19:37:39 Age [y:d:h:m:s]: 00:244:17:15:59
Block: 1129485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174659 RingCT/type: yes/0
Extra: 01107ce9da6be2c9a57be1a5b856a1634c8007aa7c93b802a47267aa98844c346402110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bfd5ca6f3d0aee5d36e4f24d50174a64661ef587b93c9c0fe2592117aef39a7 0.600000000000 1612312 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": 1129495, "vin": [ { "gen": { "height": 1129485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bfd5ca6f3d0aee5d36e4f24d50174a64661ef587b93c9c0fe2592117aef39a7" } } ], "extra": [ 1, 16, 124, 233, 218, 107, 226, 201, 165, 123, 225, 165, 184, 86, 161, 99, 76, 128, 7, 170, 124, 147, 184, 2, 164, 114, 103, 170, 152, 132, 76, 52, 100, 2, 17, 0, 0, 0, 15, 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