Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e182a5bc4f7f235e61fe4a18ef72feb68224311bca18b5540c1dbcd4b5b06f

Tx prefix hash: 4bb197e2e5363cc0e6c8044303740341f1f2dc87ca06b31d2312622ea130f1cc
Tx public key: 0241ccf5957a236762e7eb1f7732dd11220ce328e5d535621af7346b8e504a29
Timestamp: 1734154959 Timestamp [UCT]: 2024-12-14 05:42:39 Age [y:d:h:m:s]: 00:102:05:25:32
Block: 1174810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72819 RingCT/type: yes/0
Extra: 010241ccf5957a236762e7eb1f7732dd11220ce328e5d535621af7346b8e504a29021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe6d3edca29d07c5241cdf9a86b306407f403a8162efc456bae79c3b48e35a4e 0.600000000000 1661009 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": 1174820, "vin": [ { "gen": { "height": 1174810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe6d3edca29d07c5241cdf9a86b306407f403a8162efc456bae79c3b48e35a4e" } } ], "extra": [ 1, 2, 65, 204, 245, 149, 122, 35, 103, 98, 231, 235, 31, 119, 50, 221, 17, 34, 12, 227, 40, 229, 213, 53, 98, 26, 247, 52, 107, 142, 80, 74, 41, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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