Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 578ed2131d904da69477c4b417ae675b7c509061c63911c35b4d078c06f22022

Tx prefix hash: 8c9c60a73631809b385f3a3702f466f40156a69a7b1dae63bf00e1946cc84421
Tx public key: 549e43265ecd1e5bf40b8a08b39978c1f5003d537eae7ef43f53e59e2ae8aa9d
Timestamp: 1701972093 Timestamp [UCT]: 2023-12-07 18:01:33 Age [y:d:h:m:s]: 01:103:05:25:37
Block: 908098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334936 RingCT/type: yes/0
Extra: 01549e43265ecd1e5bf40b8a08b39978c1f5003d537eae7ef43f53e59e2ae8aa9d02110000000746113aa8000000000000000000

1 output(s) for total of 0.601304326000 dcy

stealth address amount amount idx
00: 0efe6e0d26f966dba17901904e620267c310cb16b4a2c3c908163ed2d5ae482d 0.601304326000 1365119 of 0

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": 908108, "vin": [ { "gen": { "height": 908098 } } ], "vout": [ { "amount": 601304326, "target": { "key": "0efe6e0d26f966dba17901904e620267c310cb16b4a2c3c908163ed2d5ae482d" } } ], "extra": [ 1, 84, 158, 67, 38, 94, 205, 30, 91, 244, 11, 138, 8, 179, 153, 120, 193, 245, 0, 61, 83, 126, 174, 126, 244, 63, 83, 229, 158, 42, 232, 170, 157, 2, 17, 0, 0, 0, 7, 70, 17, 58, 168, 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