Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30808c13b2f7738b7e5b91082f5877086e2c106b795a9835e2772312044ab67d

Tx prefix hash: 5251de78c06e445b8805786c1309013f0c55e45e9b9adba87b7175296dc8297a
Tx public key: 841625f8c74d706e1c0f72c295d8be8027d2fb98f3e656a01b06fbbfda2f16ab
Timestamp: 1736697419 Timestamp [UCT]: 2025-01-12 15:56:59 Age [y:d:h:m:s]: 00:092:22:18:13
Block: 1195846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66192 RingCT/type: yes/0
Extra: 01841625f8c74d706e1c0f72c295d8be8027d2fb98f3e656a01b06fbbfda2f16ab0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bda041ad3125f375068f3b194b63703cba9f8843f30a7da54afecae6273932ef 0.600000000000 1682439 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": 1195856, "vin": [ { "gen": { "height": 1195846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bda041ad3125f375068f3b194b63703cba9f8843f30a7da54afecae6273932ef" } } ], "extra": [ 1, 132, 22, 37, 248, 199, 77, 112, 110, 28, 15, 114, 194, 149, 216, 190, 128, 39, 210, 251, 152, 243, 230, 86, 160, 27, 6, 251, 191, 218, 47, 22, 171, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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