Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1683d5b7163704c5f4c8d74e9081564be603f9e0f87dd73cf7174ba05c7b005

Tx prefix hash: e46e0b4e0ee96e4e1d60a93828661190e6b68610574ebf973be90a6ea65338e8
Tx public key: 6c2e65f50491eca5cb57701252c42dd4f25578bcf2683c7432946e934d4c4dde
Timestamp: 1723499696 Timestamp [UCT]: 2024-08-12 21:54:56 Age [y:d:h:m:s]: 00:246:18:19:09
Block: 1086569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176254 RingCT/type: yes/0
Extra: 016c2e65f50491eca5cb57701252c42dd4f25578bcf2683c7432946e934d4c4dde021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72c4c82d47110e4aa478c3a667c0ec6409771c82c4ff5ccda84535ef403f9277 0.600000000000 1561166 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": 1086579, "vin": [ { "gen": { "height": 1086569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72c4c82d47110e4aa478c3a667c0ec6409771c82c4ff5ccda84535ef403f9277" } } ], "extra": [ 1, 108, 46, 101, 245, 4, 145, 236, 165, 203, 87, 112, 18, 82, 196, 45, 212, 242, 85, 120, 188, 242, 104, 60, 116, 50, 148, 110, 147, 77, 76, 77, 222, 2, 17, 0, 0, 0, 5, 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