Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aff38da44d88fc3b474202ba7d41c246e7a27bb5507621ac464f42c4a2c613d7

Tx prefix hash: 36932dfe611fced76d6888711127b9e3f6f029af750eb5b7f72a8bfb85fb53e5
Tx public key: da02938a0b07e274e95b3a5453402034c713a446cded80ab6ad32ec054e315dd
Timestamp: 1710571252 Timestamp [UCT]: 2024-03-16 06:40:52 Age [y:d:h:m:s]: 01:025:09:45:41
Block: 979412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279122 RingCT/type: yes/0
Extra: 01da02938a0b07e274e95b3a5453402034c713a446cded80ab6ad32ec054e315dd02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0edcb847247d76da29b8ae875516ae195398678b44a2d5c6cb7adefe4e4cca7 0.600000000000 1439445 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": 979422, "vin": [ { "gen": { "height": 979412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0edcb847247d76da29b8ae875516ae195398678b44a2d5c6cb7adefe4e4cca7" } } ], "extra": [ 1, 218, 2, 147, 138, 11, 7, 226, 116, 233, 91, 58, 84, 83, 64, 32, 52, 199, 19, 164, 70, 205, 237, 128, 171, 106, 211, 46, 192, 84, 227, 21, 221, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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