Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 578709be74a56e31992b5bcd0d41404f14eaa8fc2b77ecffd2b082a47b9c211f

Tx prefix hash: 94a683a1094d3b49e92ab37a6ce94a76f08292672a60e35a0855bf0a98cc85b9
Tx public key: 96cfa9e7f3d7f7135ff168490d4aecf1cf801dc86647557f6a9edcb8143dd350
Timestamp: 1738016484 Timestamp [UCT]: 2025-01-27 22:21:24 Age [y:d:h:m:s]: 00:143:19:08:46
Block: 1206519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102675 RingCT/type: yes/0
Extra: 0196cfa9e7f3d7f7135ff168490d4aecf1cf801dc86647557f6a9edcb8143dd3500211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4d544c8e6e213d6ba1edd8c378241ab13268f5bda4a8aaa764adce5bb446e24 0.600000000000 1693228 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": 1206529, "vin": [ { "gen": { "height": 1206519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4d544c8e6e213d6ba1edd8c378241ab13268f5bda4a8aaa764adce5bb446e24" } } ], "extra": [ 1, 150, 207, 169, 231, 243, 215, 247, 19, 95, 241, 104, 73, 13, 74, 236, 241, 207, 128, 29, 200, 102, 71, 85, 127, 106, 158, 220, 184, 20, 61, 211, 80, 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