Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70f5397c4693620cb1acc927d108d46739a213d25273eafbfaaea83597ce25e9

Tx prefix hash: 072254bdb9c524b120ae21f39710755bbc9caa8b6f7d5a9e7f761739b7dcc4c4
Tx public key: 379c305f8b404f20282d27191a130bd21992b4f7e5485efc79946ed7fa506e97
Timestamp: 1720230401 Timestamp [UCT]: 2024-07-06 01:46:41 Age [y:d:h:m:s]: 00:251:23:08:58
Block: 1059462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180034 RingCT/type: yes/0
Extra: 01379c305f8b404f20282d27191a130bd21992b4f7e5485efc79946ed7fa506e970211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e90506b5ff6d1bd771f0a67b827fe087bda6eacbcaabb2d14895c3096716fdfb 0.600000000000 1529931 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": 1059472, "vin": [ { "gen": { "height": 1059462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e90506b5ff6d1bd771f0a67b827fe087bda6eacbcaabb2d14895c3096716fdfb" } } ], "extra": [ 1, 55, 156, 48, 95, 139, 64, 79, 32, 40, 45, 39, 25, 26, 19, 11, 210, 25, 146, 180, 247, 229, 72, 94, 252, 121, 148, 110, 215, 250, 80, 110, 151, 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