Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84b00b4d52cbc074f8f9f1bb218932c498c6e4183181b576c299512ea7cb3249

Tx prefix hash: 3ab26b2da6dce69d8b80e5ae41d19443e6b6a0ede03d0d4e8e3455254eb27808
Tx public key: 6fea42f2592d0bbac3720bae36166f0a70fb13ed779f3ae4bb21ccf1044baa4f
Timestamp: 1585040729 Timestamp [UCT]: 2020-03-24 09:05:29 Age [y:d:h:m:s]: 04:334:04:00:03
Block: 87816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135551 RingCT/type: yes/0
Extra: 016fea42f2592d0bbac3720bae36166f0a70fb13ed779f3ae4bb21ccf1044baa4f02110000015f86362411000000000000000000

1 output(s) for total of 314.072503501000 dcy

stealth address amount amount idx
00: 478ad74a4ca8cd6618c4ff3bfe308c980443640c3c43dafb90d51bc4b208c287 314.072503501000 158074 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": 87826, "vin": [ { "gen": { "height": 87816 } } ], "vout": [ { "amount": 314072503501, "target": { "key": "478ad74a4ca8cd6618c4ff3bfe308c980443640c3c43dafb90d51bc4b208c287" } } ], "extra": [ 1, 111, 234, 66, 242, 89, 45, 11, 186, 195, 114, 11, 174, 54, 22, 111, 10, 112, 251, 19, 237, 119, 159, 58, 228, 187, 33, 204, 241, 4, 75, 170, 79, 2, 17, 0, 0, 1, 95, 134, 54, 36, 17, 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