Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 598d074b7a28851b4cf83a43f2dabdd7fa871178d14379401a818ec978109ecd

Tx prefix hash: 6252e325c8c1ae30b971c84364d27853b297f7e471d7220859e767694280f73c
Tx public key: 6d6422bbf2af89344e88fa8042b9a48f0701a19fe193f9c5dbac99f2ae18a277
Timestamp: 1736404194 Timestamp [UCT]: 2025-01-09 06:29:54 Age [y:d:h:m:s]: 00:161:11:22:53
Block: 1193417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115100 RingCT/type: yes/0
Extra: 016d6422bbf2af89344e88fa8042b9a48f0701a19fe193f9c5dbac99f2ae18a277021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f19c2e0811554b0a380bdccc1e542c836a191d35dbd4cc8c7c3f1fb752d513b7 0.600000000000 1679978 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": 1193427, "vin": [ { "gen": { "height": 1193417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f19c2e0811554b0a380bdccc1e542c836a191d35dbd4cc8c7c3f1fb752d513b7" } } ], "extra": [ 1, 109, 100, 34, 187, 242, 175, 137, 52, 78, 136, 250, 128, 66, 185, 164, 143, 7, 1, 161, 159, 225, 147, 249, 197, 219, 172, 153, 242, 174, 24, 162, 119, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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