Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 817e534e16518191d96bd82f09fd4f01feb33b2ca0f6e680549d57241882054b

Tx prefix hash: 4cec85b5871bd2b6c0fea222ab306395bc7b00a0c014e09905e8d0ba6347624f
Tx public key: 431fbbcf71c7a753c8fb0dc99279f09ba4a8e9bba53830cec60c2845b337c380
Timestamp: 1723724359 Timestamp [UCT]: 2024-08-15 12:19:19 Age [y:d:h:m:s]: 01:085:09:30:20
Block: 1088437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319487 RingCT/type: yes/0
Extra: 01431fbbcf71c7a753c8fb0dc99279f09ba4a8e9bba53830cec60c2845b337c380021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a744c65af06e3410957f8928a2e44f70296313b24e3c7cc5522212ebd42c063d 0.600000000000 1563054 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": 1088447, "vin": [ { "gen": { "height": 1088437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a744c65af06e3410957f8928a2e44f70296313b24e3c7cc5522212ebd42c063d" } } ], "extra": [ 1, 67, 31, 187, 207, 113, 199, 167, 83, 200, 251, 13, 201, 146, 121, 240, 155, 164, 168, 233, 187, 165, 56, 48, 206, 198, 12, 40, 69, 179, 55, 195, 128, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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