Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 257eaddf5f3e1c2fd872c0545a198187a4d7551dca92163203bfadd3b5687102

Tx prefix hash: 12a70ec783a45e7c2f8c65a70e1f092325ce3b0e6b76400bc81cb71e4a2e2d6c
Tx public key: 148a3201ae5ca31649b19c892783f819d2682b414a3c4b1cb78bc1cd2e2a849f
Timestamp: 1580268649 Timestamp [UCT]: 2020-01-29 03:30:49 Age [y:d:h:m:s]: 04:306:17:16:19
Block: 54807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109702 RingCT/type: yes/0
Extra: 01148a3201ae5ca31649b19c892783f819d2682b414a3c4b1cb78bc1cd2e2a849f02110000000149b77a3d000000000000000000

1 output(s) for total of 404.019645714000 dcy

stealth address amount amount idx
00: 807ae7721c0a63771335e9778ea2f81a0ac70ce1149713421b13d4aa3599d185 404.019645714000 101298 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": 54817, "vin": [ { "gen": { "height": 54807 } } ], "vout": [ { "amount": 404019645714, "target": { "key": "807ae7721c0a63771335e9778ea2f81a0ac70ce1149713421b13d4aa3599d185" } } ], "extra": [ 1, 20, 138, 50, 1, 174, 92, 163, 22, 73, 177, 156, 137, 39, 131, 248, 25, 210, 104, 43, 65, 74, 60, 75, 28, 183, 139, 193, 205, 46, 42, 132, 159, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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