Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8f6635ce8f884190921b3da08b8427f08f687dadafd09539e533d1c1f13f2b6

Tx prefix hash: 2ab293a0ed8ebce1dd2c7dc6bc6f41866444ee8dfc51fd6e84afd69e30deeaa4
Tx public key: ed67437b7885deba967cd08c68a15f8771f16a7a2ad1c31e568be7fbe7147df3
Timestamp: 1711591382 Timestamp [UCT]: 2024-03-28 02:03:02 Age [y:d:h:m:s]: 00:338:01:34:31
Block: 987858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241667 RingCT/type: yes/0
Extra: 01ed67437b7885deba967cd08c68a15f8771f16a7a2ad1c31e568be7fbe7147df302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f022a143b9ea82ce7325fa89f9ca1dd2d17c50896a29c4ca1443799adcb38751 0.600000000000 1448119 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": 987868, "vin": [ { "gen": { "height": 987858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f022a143b9ea82ce7325fa89f9ca1dd2d17c50896a29c4ca1443799adcb38751" } } ], "extra": [ 1, 237, 103, 67, 123, 120, 133, 222, 186, 150, 124, 208, 140, 104, 161, 95, 135, 113, 241, 106, 122, 42, 209, 195, 30, 86, 139, 231, 251, 231, 20, 125, 243, 2, 17, 0, 0, 0, 3, 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