Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 445454f57d42490aee37f31525976d4ee46b8e1a9255cbbee0664560bfdf9abc

Tx prefix hash: 387e2f7cb8ea2caf821d6d5b0ea77f15c2869c76d412a9f52ee4560f76c63f44
Tx public key: 177c54b0c2a3df371d71c102723bd971a6a2d2f755b30f28cc0edab18fcfb690
Timestamp: 1697431310 Timestamp [UCT]: 2023-10-16 04:41:50 Age [y:d:h:m:s]: 01:185:07:42:36
Block: 870653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393488 RingCT/type: yes/0
Extra: 01177c54b0c2a3df371d71c102723bd971a6a2d2f755b30f28cc0edab18fcfb690021100000004faf35c9c000000000000000000

1 output(s) for total of 0.800138582000 dcy

stealth address amount amount idx
00: 797423175828616cb1d4951a1d18a879baf2ddc05478059d6be53b4f2db6956d 0.800138582000 1325536 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": 870663, "vin": [ { "gen": { "height": 870653 } } ], "vout": [ { "amount": 800138582, "target": { "key": "797423175828616cb1d4951a1d18a879baf2ddc05478059d6be53b4f2db6956d" } } ], "extra": [ 1, 23, 124, 84, 176, 194, 163, 223, 55, 29, 113, 193, 2, 114, 59, 217, 113, 166, 162, 210, 247, 85, 179, 15, 40, 204, 14, 218, 177, 143, 207, 182, 144, 2, 17, 0, 0, 0, 4, 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