Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d747d6d950712ebda861f27966f2f08c6108870256a1ca57086f21e93c80df66

Tx prefix hash: 8f56880bbc50a67cd1af71d27577d1aedb7dd7b961431467e3a5c7ed0f3c263d
Tx public key: 5f28a1a5a5e9e4b4f851bc4a51a3b85f14f2e6fa1f1e9a865c383bf77be7489e
Timestamp: 1749370759 Timestamp [UCT]: 2025-06-08 08:19:19 Age [y:d:h:m:s]: 00:158:04:05:31
Block: 1300504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110722 RingCT/type: yes/0
Extra: 015f28a1a5a5e9e4b4f851bc4a51a3b85f14f2e6fa1f1e9a865c383bf77be7489e021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fdd1528d332e3fae395a49d18af93929e0f84a7556dd8c61ab8670ed6bded97 0.600000000000 1788053 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": 1300514, "vin": [ { "gen": { "height": 1300504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fdd1528d332e3fae395a49d18af93929e0f84a7556dd8c61ab8670ed6bded97" } } ], "extra": [ 1, 95, 40, 161, 165, 165, 233, 228, 180, 248, 81, 188, 74, 81, 163, 184, 95, 20, 242, 230, 250, 31, 30, 154, 134, 92, 56, 59, 247, 123, 231, 72, 158, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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