Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f73560cada357eb7c1f56df57a9500521173d74f8fdd691ef418216b0b5af6bf

Tx prefix hash: b09bd5d7945a8b88ef73b778e071f27aa6f44e8f8ed532225379fd9892eb0050
Tx public key: 0e4672fd7eb421471c9d9529c9f05b929e0c3264a26df45dbc8c5367f71dfca9
Timestamp: 1631550280 Timestamp [UCT]: 2021-09-13 16:24:40 Age [y:d:h:m:s]: 03:107:04:12:03
Block: 333050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 852197 RingCT/type: yes/0
Extra: 010e4672fd7eb421471c9d9529c9f05b929e0c3264a26df45dbc8c5367f71dfca902110000001dfdc024ec000000000000000000

1 output(s) for total of 48.357911536000 dcy

stealth address amount amount idx
00: 556a2ae532a9a3542ee468a2b2e6e513e5be09181a58ca6574fcfad159939a3a 48.357911536000 687451 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": 333060, "vin": [ { "gen": { "height": 333050 } } ], "vout": [ { "amount": 48357911536, "target": { "key": "556a2ae532a9a3542ee468a2b2e6e513e5be09181a58ca6574fcfad159939a3a" } } ], "extra": [ 1, 14, 70, 114, 253, 126, 180, 33, 71, 28, 157, 149, 41, 201, 240, 91, 146, 158, 12, 50, 100, 162, 109, 244, 93, 188, 140, 83, 103, 247, 29, 252, 169, 2, 17, 0, 0, 0, 29, 253, 192, 36, 236, 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