Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccec432a3a12530556154a64e36191d0911bae175e7f19f0bd6b0feb3efcc90b

Tx prefix hash: 04a743743a5c3fbe7caab3b30642cc78d3ceb047654b75cb52a66d2620aee020
Tx public key: a605ed683092e3f5480733bae33f982b29a6ec8dd4c869f545084f3d53a4d309
Timestamp: 1702652084 Timestamp [UCT]: 2023-12-15 14:54:44 Age [y:d:h:m:s]: 01:151:20:53:47
Block: 913730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369703 RingCT/type: yes/0
Extra: 01a605ed683092e3f5480733bae33f982b29a6ec8dd4c869f545084f3d53a4d30902110000001033af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04f04a93838a0a4487f70ae3a51f99b4f9b8bb38568a42cec916323661502fb1 0.600000000000 1371006 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": 913740, "vin": [ { "gen": { "height": 913730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04f04a93838a0a4487f70ae3a51f99b4f9b8bb38568a42cec916323661502fb1" } } ], "extra": [ 1, 166, 5, 237, 104, 48, 146, 227, 245, 72, 7, 51, 186, 227, 63, 152, 43, 41, 166, 236, 141, 212, 200, 105, 245, 69, 8, 79, 61, 83, 164, 211, 9, 2, 17, 0, 0, 0, 16, 51, 175, 153, 244, 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