Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e003798595b4c50796fb8879cc3895a8425b82f3ea3c71685414fadd22abbc0f

Tx prefix hash: 6a695e545bc13643a2863d8b40a89842f58863924ec67b9acf5c0a17e48aa701
Tx public key: 3bc60b067a095e4ab20f6ecdc96ff6778095e51e78ab1f6794f621516e2cc35e
Timestamp: 1699813339 Timestamp [UCT]: 2023-11-12 18:22:19 Age [y:d:h:m:s]: 01:071:10:09:13
Block: 890205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312409 RingCT/type: yes/0
Extra: 013bc60b067a095e4ab20f6ecdc96ff6778095e51e78ab1f6794f621516e2cc35e021100000001faf35c9c000000000000000000

1 output(s) for total of 0.689257168000 dcy

stealth address amount amount idx
00: e91094801bac758c69d485230ab0a1a7c2548fcc2607ee85a113688d9e844ac2 0.689257168000 1346226 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": 890215, "vin": [ { "gen": { "height": 890205 } } ], "vout": [ { "amount": 689257168, "target": { "key": "e91094801bac758c69d485230ab0a1a7c2548fcc2607ee85a113688d9e844ac2" } } ], "extra": [ 1, 59, 198, 11, 6, 122, 9, 94, 74, 178, 15, 110, 205, 201, 111, 246, 119, 128, 149, 229, 30, 120, 171, 31, 103, 148, 246, 33, 81, 110, 44, 195, 94, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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