Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0fc9508d9d79347454c0706aab81e5f1e48320da3e50cbe7b016c0c8bb845a8

Tx prefix hash: 95aa8c57c76a00b7261384aa0db0b31bb260088683b595edfcb32cadc77a8b87
Tx public key: 42a62773c8f1123cae55f6ffedf139cf4d2df93d45d1ef23a7863a4c55ff864c
Timestamp: 1719815078 Timestamp [UCT]: 2024-07-01 06:24:38 Age [y:d:h:m:s]: 00:277:10:35:42
Block: 1056016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198241 RingCT/type: yes/0
Extra: 0142a62773c8f1123cae55f6ffedf139cf4d2df93d45d1ef23a7863a4c55ff864c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08a86a9271fda8afdea9bfbfb4ba6d71e7bb20380a831f73438d6e123fa55178 0.600000000000 1526427 of 15

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": 1056026, "vin": [ { "gen": { "height": 1056016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08a86a9271fda8afdea9bfbfb4ba6d71e7bb20380a831f73438d6e123fa55178" } } ], "extra": [ 1, 66, 166, 39, 115, 200, 241, 18, 60, 174, 85, 246, 255, 237, 241, 57, 207, 77, 45, 249, 61, 69, 209, 239, 35, 167, 134, 58, 76, 85, 255, 134, 76, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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