Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba90588e11c81bba526c55e11d6897bf024b83b591c3718d3b49336c9cb68983

Tx prefix hash: a3cd266ce4867288596b7606e42125d742199b55dc2e869d87ab6cea2f279f3d
Tx public key: 828e3b2a853efb6fd0cda7335533137f6a400ad3aecb22f897cc7eb6a5720375
Timestamp: 1736173042 Timestamp [UCT]: 2025-01-06 14:17:22 Age [y:d:h:m:s]: 00:081:09:46:34
Block: 1191515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57947 RingCT/type: yes/0
Extra: 01828e3b2a853efb6fd0cda7335533137f6a400ad3aecb22f897cc7eb6a57203750211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 509b7bb497b85cc47d48813f4d8eae6c76276e832fbc2cb654300b91d6ad1c00 0.600000000000 1678054 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": 1191525, "vin": [ { "gen": { "height": 1191515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "509b7bb497b85cc47d48813f4d8eae6c76276e832fbc2cb654300b91d6ad1c00" } } ], "extra": [ 1, 130, 142, 59, 42, 133, 62, 251, 111, 208, 205, 167, 51, 85, 51, 19, 127, 106, 64, 10, 211, 174, 203, 34, 248, 151, 204, 126, 182, 165, 114, 3, 117, 2, 17, 0, 0, 0, 4, 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