Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0811f64ae1ab3b1220cb97d37fb9f3351902e90f596d97863e4730fcaa60ec21

Tx prefix hash: f2e3b72472287891a63b3554a1602de3d06bc9e3b762ff5fedd08e9bc2a67187
Tx public key: 573dcd71b85887f08e47c543143fd75875ea2b49588db2f82d7ff7357b449312
Timestamp: 1577233717 Timestamp [UCT]: 2019-12-25 00:28:37 Age [y:d:h:m:s]: 05:009:13:10:46
Block: 31088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156823 RingCT/type: yes/0
Extra: 01573dcd71b85887f08e47c543143fd75875ea2b49588db2f82d7ff7357b4493120211000000034ac5aa02000000000000000000

1 output(s) for total of 484.173382405000 dcy

stealth address amount amount idx
00: 9905c4f83a50b03b711655d3d2f6d0ef9b8021271e786d19bf84728ca3c5c97f 484.173382405000 51378 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": 31098, "vin": [ { "gen": { "height": 31088 } } ], "vout": [ { "amount": 484173382405, "target": { "key": "9905c4f83a50b03b711655d3d2f6d0ef9b8021271e786d19bf84728ca3c5c97f" } } ], "extra": [ 1, 87, 61, 205, 113, 184, 88, 135, 240, 142, 71, 197, 67, 20, 63, 215, 88, 117, 234, 43, 73, 88, 141, 178, 248, 45, 127, 247, 53, 123, 68, 147, 18, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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