Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78a4ad36b16688374c57bfed14b358b19b87dcd55a4df0815416b82d99fc196e

Tx prefix hash: 8e1f547824d28fcfe12c6ff9481100515607d3ffb30811d5c72fb9ba16cb01d1
Tx public key: 8a692f4095131435220ac9c9947ed90d2a0bbbe80b470b06f3c805b2a4ecfce4
Timestamp: 1681351541 Timestamp [UCT]: 2023-04-13 02:05:41 Age [y:d:h:m:s]: 02:206:08:27:19
Block: 737374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 667352 RingCT/type: yes/0
Extra: 018a692f4095131435220ac9c9947ed90d2a0bbbe80b470b06f3c805b2a4ecfce40211000000015029cbac000000000000000000

1 output(s) for total of 2.211943661000 dcy

stealth address amount amount idx
00: c7f1aef46c383686bea78ec760f09ae26b6231bcee8cbeb6e98c6a9485a932f5 2.211943661000 1183923 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": 737384, "vin": [ { "gen": { "height": 737374 } } ], "vout": [ { "amount": 2211943661, "target": { "key": "c7f1aef46c383686bea78ec760f09ae26b6231bcee8cbeb6e98c6a9485a932f5" } } ], "extra": [ 1, 138, 105, 47, 64, 149, 19, 20, 53, 34, 10, 201, 201, 148, 126, 217, 13, 42, 11, 187, 232, 11, 71, 11, 6, 243, 200, 5, 178, 164, 236, 252, 228, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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