Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fecd5f2275d07d4c33fd7d75df9225ef4083ef4521798ee4e457bf3c2dd0cff8

Tx prefix hash: cbc2c196912a51fae99cb51ef5283d0224cc823391d553ff5828ec57c00d3ee6
Tx public key: 7052efbc4b7041b45fc576d8582929af6849ccbb5c0f0d7f7cda81ff9f08526b
Timestamp: 1712657518 Timestamp [UCT]: 2024-04-09 10:11:58 Age [y:d:h:m:s]: 00:218:01:36:14
Block: 996656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156137 RingCT/type: yes/0
Extra: 017052efbc4b7041b45fc576d8582929af6849ccbb5c0f0d7f7cda81ff9f08526b02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e586fde9e3eadcd2fc95707098f1f5d925ecb389f180dc518e60bc96a4c5c6ea 0.600000000000 1457082 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": 996666, "vin": [ { "gen": { "height": 996656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e586fde9e3eadcd2fc95707098f1f5d925ecb389f180dc518e60bc96a4c5c6ea" } } ], "extra": [ 1, 112, 82, 239, 188, 75, 112, 65, 180, 95, 197, 118, 216, 88, 41, 41, 175, 104, 73, 204, 187, 92, 15, 13, 127, 124, 218, 129, 255, 159, 8, 82, 107, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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