Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a38800e3e592187f025b4da26a2c1dec2b259fdcd104879a55e8a2ef0b1b4599

Tx prefix hash: ea56ab261276f422bfcb762d42b5fc56b5aca65ee7b57f68e6f4926f169ccef0
Tx public key: f7f54929328951f4f8e3cd231cd4f6debeb179f5afc39fe0ea9179e56d95a995
Timestamp: 1705051834 Timestamp [UCT]: 2024-01-12 09:30:34 Age [y:d:h:m:s]: 01:083:19:35:33
Block: 933616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320994 RingCT/type: yes/0
Extra: 01f7f54929328951f4f8e3cd231cd4f6debeb179f5afc39fe0ea9179e56d95a99502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81f45dde6fe5b465708d98d671e71a608d00502e2b10f55e2a1f8ec2df4d3225 0.600000000000 1391584 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": 933626, "vin": [ { "gen": { "height": 933616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81f45dde6fe5b465708d98d671e71a608d00502e2b10f55e2a1f8ec2df4d3225" } } ], "extra": [ 1, 247, 245, 73, 41, 50, 137, 81, 244, 248, 227, 205, 35, 28, 212, 246, 222, 190, 177, 121, 245, 175, 195, 159, 224, 234, 145, 121, 229, 109, 149, 169, 149, 2, 17, 0, 0, 0, 1, 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