Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 974e00cf80cc8aefa85ca04c61452f617532cfb2807acc412bf403521f6de384

Tx prefix hash: 791ece2bb797791592127c635e0138e30a150be7703cbe1b08d3e6713f9ae5b8
Tx public key: f7b0271e1a1e4d2c0fa1fee489dc82d6ee5375c691f185faf6f8c9e277a94db9
Timestamp: 1762926306 Timestamp [UCT]: 2025-11-12 05:45:06 Age [y:d:h:m:s]: 00:039:20:31:20
Block: 1410308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28541 RingCT/type: yes/0
Extra: 01f7b0271e1a1e4d2c0fa1fee489dc82d6ee5375c691f185faf6f8c9e277a94db90211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3df33c45d8e1df8fd942e3ac4df28237e51a4f80f65091c01d05f3b8fb62f8b6 0.600000000000 1898759 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": 1410318, "vin": [ { "gen": { "height": 1410308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3df33c45d8e1df8fd942e3ac4df28237e51a4f80f65091c01d05f3b8fb62f8b6" } } ], "extra": [ 1, 247, 176, 39, 30, 26, 30, 77, 44, 15, 161, 254, 228, 137, 220, 130, 214, 238, 83, 117, 198, 145, 241, 133, 250, 246, 248, 201, 226, 119, 169, 77, 185, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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