Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 562c656cbdf58f94a980731d14710fd076a9c35b680229630ef17b9e0b1074c9

Tx prefix hash: 75ba628ff2c96ab7f8b4e1f013317164c7c02c44a9264530ee6c5e2ca468cdb9
Tx public key: 318f396594c65df76d7af44d8bdf91aa60bda95ad595ae714f91b03e48f110db
Timestamp: 1744724461 Timestamp [UCT]: 2025-04-15 13:41:01 Age [y:d:h:m:s]: 00:024:22:29:00
Block: 1262024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17839 RingCT/type: yes/0
Extra: 01318f396594c65df76d7af44d8bdf91aa60bda95ad595ae714f91b03e48f110db021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 936f965020dbaac4d2ace87c90148699bacf9f8a768de4055cd16bcfdb0b2be9 0.600000000000 1749201 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": 1262034, "vin": [ { "gen": { "height": 1262024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "936f965020dbaac4d2ace87c90148699bacf9f8a768de4055cd16bcfdb0b2be9" } } ], "extra": [ 1, 49, 143, 57, 101, 148, 198, 93, 247, 109, 122, 244, 77, 139, 223, 145, 170, 96, 189, 169, 90, 213, 149, 174, 113, 79, 145, 176, 62, 72, 241, 16, 219, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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