Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 368973fa7146162c301339c8d11b043397c94c945bc7f5db2901a7af4e8241af

Tx prefix hash: 6f33b16f2af24cb6dc80ed6ae12f94b8ee2aabcbb7143e18628f8bafa30eb404
Tx public key: 5126aa8e9c2e3deedbfd42fce670a8d0a634ad26c9a1c4aeef580d10632f8b26
Timestamp: 1582481964 Timestamp [UCT]: 2020-02-23 18:19:24 Age [y:d:h:m:s]: 04:308:14:22:29
Block: 70951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113228 RingCT/type: yes/0
Extra: 015126aa8e9c2e3deedbfd42fce670a8d0a634ad26c9a1c4aeef580d10632f8b260211000000104ac5aa02000000000000000000

1 output(s) for total of 357.199371548000 dcy

stealth address amount amount idx
00: e7a1cbb7da3c59020020c6634a4ce966a05d87212dd0f49c28364d22745da4e5 357.199371548000 131134 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": 70961, "vin": [ { "gen": { "height": 70951 } } ], "vout": [ { "amount": 357199371548, "target": { "key": "e7a1cbb7da3c59020020c6634a4ce966a05d87212dd0f49c28364d22745da4e5" } } ], "extra": [ 1, 81, 38, 170, 142, 156, 46, 61, 238, 219, 253, 66, 252, 230, 112, 168, 208, 166, 52, 173, 38, 201, 161, 196, 174, 239, 88, 13, 16, 99, 47, 139, 38, 2, 17, 0, 0, 0, 16, 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