Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4be1a18c4cc9975d3d122c6e9fefa1d364062ce775f3bf975df70f232cf88f75

Tx prefix hash: dd03129f44830711ddad63924abbcfc9335ee4a08adaf1c50a42b8657ea2a09a
Tx public key: d4b501938253518cecde5242a03221ab27cde11fb9c971a0be3c3ab0e2b9ab87
Timestamp: 1669507557 Timestamp [UCT]: 2022-11-27 00:05:57 Age [y:d:h:m:s]: 02:093:16:13:30
Block: 639845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588635 RingCT/type: yes/0
Extra: 01d4b501938253518cecde5242a03221ab27cde11fb9c971a0be3c3ab0e2b9ab8702110000000333af99f4000000000000000000

1 output(s) for total of 4.655088094000 dcy

stealth address amount amount idx
00: 2f27b8eabe314f0bac438684ba1c16e78b658f5dd573ad38d0d796165b456955 4.655088094000 1079530 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": 639855, "vin": [ { "gen": { "height": 639845 } } ], "vout": [ { "amount": 4655088094, "target": { "key": "2f27b8eabe314f0bac438684ba1c16e78b658f5dd573ad38d0d796165b456955" } } ], "extra": [ 1, 212, 181, 1, 147, 130, 83, 81, 140, 236, 222, 82, 66, 160, 50, 33, 171, 39, 205, 225, 31, 185, 201, 113, 160, 190, 60, 58, 176, 226, 185, 171, 135, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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