Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f28c3e7f0ad2fa4035e36311b7c829194f33483aa18d2178560d09dcd0a4bc7

Tx prefix hash: 491c259197c671b24ba9dbf770955f9df7f58e1c731fba3cbe8985ae71383354
Tx public key: 36e8023dfba92728ac49cc71c79a1ad36b87f26b99d33881aff3c9efcdfbc67c
Timestamp: 1672827464 Timestamp [UCT]: 2023-01-04 10:17:44 Age [y:d:h:m:s]: 01:333:12:58:29
Block: 667342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499396 RingCT/type: yes/0
Extra: 0136e8023dfba92728ac49cc71c79a1ad36b87f26b99d33881aff3c9efcdfbc67c02110000000233af99f4000000000000000000

1 output(s) for total of 3.774147667000 dcy

stealth address amount amount idx
00: fa27a76016f8781d2c4128066c3d8ba0b60f18ae724eec1df124fe7439aa0df8 3.774147667000 1108511 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": 667352, "vin": [ { "gen": { "height": 667342 } } ], "vout": [ { "amount": 3774147667, "target": { "key": "fa27a76016f8781d2c4128066c3d8ba0b60f18ae724eec1df124fe7439aa0df8" } } ], "extra": [ 1, 54, 232, 2, 61, 251, 169, 39, 40, 172, 73, 204, 113, 199, 154, 26, 211, 107, 135, 242, 107, 153, 211, 56, 129, 175, 243, 201, 239, 205, 251, 198, 124, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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