Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f779a011e5ed18b10e0f049d4e29599f31d98fae99840c8597066cc3d872ed5

Tx prefix hash: 3ac7c600739e8b434e01fe5a26661573e10ae132134f3f400988513b01e6cfc4
Tx public key: f9477dfb2ab98bae60a5f933d3ca088a6b00614ee30bf0a180f9ee5ce0633421
Timestamp: 1741646306 Timestamp [UCT]: 2025-03-10 22:38:26 Age [y:d:h:m:s]: 00:327:16:28:55
Block: 1236562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231843 RingCT/type: yes/0
Extra: 01f9477dfb2ab98bae60a5f933d3ca088a6b00614ee30bf0a180f9ee5ce06334210211000000121f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f0c7a2c1221404cd4dd7ffe2d08b67e85bcac4af60c0df6b39359e1653a3ba2 0.600000000000 1723509 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": 1236572, "vin": [ { "gen": { "height": 1236562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f0c7a2c1221404cd4dd7ffe2d08b67e85bcac4af60c0df6b39359e1653a3ba2" } } ], "extra": [ 1, 249, 71, 125, 251, 42, 185, 139, 174, 96, 165, 249, 51, 211, 202, 8, 138, 107, 0, 97, 78, 227, 11, 240, 161, 128, 249, 238, 92, 224, 99, 52, 33, 2, 17, 0, 0, 0, 18, 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