Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34168b084ec99a582fa1808e7d84b397eaa7748c7de40a838a40ec1a78155d93

Tx prefix hash: 03a6e7a0495ce5037623f89f12b8063432439ee188bfffaf97ea7ea6a2e2dd66
Tx public key: 2528316db81ba895a103dfe843b6ef4700558d1fadf04c05992ad46d3893b034
Timestamp: 1644590194 Timestamp [UCT]: 2022-02-11 14:36:34 Age [y:d:h:m:s]: 02:281:12:07:07
Block: 436375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720447 RingCT/type: yes/0
Extra: 012528316db81ba895a103dfe843b6ef4700558d1fadf04c05992ad46d3893b0340211000000f2bf7ee4e7000000000000000000

1 output(s) for total of 21.984104301000 dcy

stealth address amount amount idx
00: 46e36fc69b2b4f0c0b73ddc17acd0613778381f5bfa077b1fd7b759e68a64652 21.984104301000 847736 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": 436385, "vin": [ { "gen": { "height": 436375 } } ], "vout": [ { "amount": 21984104301, "target": { "key": "46e36fc69b2b4f0c0b73ddc17acd0613778381f5bfa077b1fd7b759e68a64652" } } ], "extra": [ 1, 37, 40, 49, 109, 184, 27, 168, 149, 161, 3, 223, 232, 67, 182, 239, 71, 0, 85, 141, 31, 173, 240, 76, 5, 153, 42, 212, 109, 56, 147, 176, 52, 2, 17, 0, 0, 0, 242, 191, 126, 228, 231, 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