Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35524bed31b48e34b3fce5d407fbd68dd8824ccd20ca10490bca09ecb3f4db1a

Tx prefix hash: 5146adb354cfe00fd6850c7e50829bbc69f1ac6861b40aa5ca6b97ed8ec84262
Tx public key: 5bb3b35576d819d20a0e080c1771bb5f3d908e6cd71ac0cef81b27436de9ca63
Timestamp: 1750101956 Timestamp [UCT]: 2025-06-16 19:25:56 Age [y:d:h:m:s]: 00:222:12:23:28
Block: 1306447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156726 RingCT/type: yes/0
Extra: 015bb3b35576d819d20a0e080c1771bb5f3d908e6cd71ac0cef81b27436de9ca630211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9482f2941450c663aa8088ea384d3bb66c55ab4e7395a2d8b2d98024ffe884c 0.600000000000 1794054 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": 1306457, "vin": [ { "gen": { "height": 1306447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9482f2941450c663aa8088ea384d3bb66c55ab4e7395a2d8b2d98024ffe884c" } } ], "extra": [ 1, 91, 179, 179, 85, 118, 216, 25, 210, 10, 14, 8, 12, 23, 113, 187, 95, 61, 144, 142, 108, 215, 26, 192, 206, 248, 27, 39, 67, 109, 233, 202, 99, 2, 17, 0, 0, 0, 2, 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