Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c263155325d39bdc9b3647d729110d7521b10b109b96bb50c0f6b677b0a6da2

Tx prefix hash: 11a503a345f3fb9b0a046c9cfc377d4f52d2a916f5dd05fa1cbac355b8a61213
Tx public key: e88ce2998497f2ba122b6b3d493824f13140d701fc73f6ec0748d12947c6e516
Timestamp: 1674135865 Timestamp [UCT]: 2023-01-19 13:44:25 Age [y:d:h:m:s]: 02:036:23:27:53
Block: 678176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548062 RingCT/type: yes/0
Extra: 01e88ce2998497f2ba122b6b3d493824f13140d701fc73f6ec0748d12947c6e51602110000000152542ceb000000000000000000

1 output(s) for total of 3.474732153000 dcy

stealth address amount amount idx
00: 0641bcfdd15296492711e095d05458a3fb45dc53b25b540ddd77a3a56e6070ea 3.474732153000 1120013 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": 678186, "vin": [ { "gen": { "height": 678176 } } ], "vout": [ { "amount": 3474732153, "target": { "key": "0641bcfdd15296492711e095d05458a3fb45dc53b25b540ddd77a3a56e6070ea" } } ], "extra": [ 1, 232, 140, 226, 153, 132, 151, 242, 186, 18, 43, 107, 61, 73, 56, 36, 241, 49, 64, 215, 1, 252, 115, 246, 236, 7, 72, 209, 41, 71, 198, 229, 22, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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