Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f00a448dca00084cb8b1ecfe466a14f5e47db1fcbcbb33886ad1ef46d022006

Tx prefix hash: f442b3a919c1a6cd04afd7ac9c67788508eb202c787064c83f041e48232f7f9b
Tx public key: c9a36f5f7d73e86200e8505ea62a33224c6aca4e046ba8f162bc2cd97292be4b
Timestamp: 1737892205 Timestamp [UCT]: 2025-01-26 11:50:05 Age [y:d:h:m:s]: 00:328:15:36:46
Block: 1205691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232490 RingCT/type: yes/0
Extra: 01c9a36f5f7d73e86200e8505ea62a33224c6aca4e046ba8f162bc2cd97292be4b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24635afd64ba1bd2d553261c307bd8e8688b303d5eb9275f033ee6b38fbf24c7 0.600000000000 1692390 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": 1205701, "vin": [ { "gen": { "height": 1205691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24635afd64ba1bd2d553261c307bd8e8688b303d5eb9275f033ee6b38fbf24c7" } } ], "extra": [ 1, 201, 163, 111, 95, 125, 115, 232, 98, 0, 232, 80, 94, 166, 42, 51, 34, 76, 106, 202, 78, 4, 107, 168, 241, 98, 188, 44, 217, 114, 146, 190, 75, 2, 17, 0, 0, 0, 5, 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