Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 327eadff3911100804963eac7a798874dc59e9cc3772da193841cc45577a4a8d

Tx prefix hash: 0cb54f2f3feada5ca9ae18cad36b20a6ab7f00e7f1202e00895ce9679dd46aa8
Tx public key: 7a4fd7a028da63a7b9f71bb38b6d6adf56286154ee63463c53f8109faf5b72a4
Timestamp: 1717922053 Timestamp [UCT]: 2024-06-09 08:34:13 Age [y:d:h:m:s]: 00:144:04:48:48
Block: 1040331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103220 RingCT/type: yes/0
Extra: 017a4fd7a028da63a7b9f71bb38b6d6adf56286154ee63463c53f8109faf5b72a40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7362438ae60607ac61df7369bba8788662ba05b7b4ed56fa2ca1d2119561acf9 0.600000000000 1508988 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": 1040341, "vin": [ { "gen": { "height": 1040331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7362438ae60607ac61df7369bba8788662ba05b7b4ed56fa2ca1d2119561acf9" } } ], "extra": [ 1, 122, 79, 215, 160, 40, 218, 99, 167, 185, 247, 27, 179, 139, 109, 106, 223, 86, 40, 97, 84, 238, 99, 70, 60, 83, 248, 16, 159, 175, 91, 114, 164, 2, 17, 0, 0, 0, 6, 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