Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cf409c43df63a13cb9e4ba774886b4755faf1115f1ef1c0143535c13559ca53

Tx prefix hash: 9d950ca49f5d2c092dd0626c1e85eb7ce81cfe86880f87528fe00d318d0c5143
Tx public key: b61be9fc441bcc493364a3077203d7625b8c8d0cd2f093fe457b9d83c5761c59
Timestamp: 1759131395 Timestamp [UCT]: 2025-09-29 07:36:35 Age [y:d:h:m:s]: 00:044:13:28:38
Block: 1378853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31911 RingCT/type: yes/0
Extra: 01b61be9fc441bcc493364a3077203d7625b8c8d0cd2f093fe457b9d83c5761c5902110000000da5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a8ac2962674c250912cadda0f37d2f0c0c8bb2d936fbaed955ea5db17e5c190 0.600000000000 1866948 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": 1378863, "vin": [ { "gen": { "height": 1378853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a8ac2962674c250912cadda0f37d2f0c0c8bb2d936fbaed955ea5db17e5c190" } } ], "extra": [ 1, 182, 27, 233, 252, 68, 27, 204, 73, 51, 100, 163, 7, 114, 3, 215, 98, 91, 140, 141, 12, 210, 240, 147, 254, 69, 123, 157, 131, 197, 118, 28, 89, 2, 17, 0, 0, 0, 13, 165, 220, 205, 121, 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