Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a100660bd1bbe31d16aa6a1f61548746eeeece65e2bf7e0a854be63c9fd4583

Tx prefix hash: 29730e06f8aa7b9b81df5cc66e305472617c1d962f640c0c058f6999e54c2308
Tx public key: 3fa7f8bcd6aeb670137934a2f8f155c4b286e5595338a0f5878a6fcb3383ad8e
Timestamp: 1697125693 Timestamp [UCT]: 2023-10-12 15:48:13 Age [y:d:h:m:s]: 02:109:22:19:52
Block: 868136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598089 RingCT/type: yes/0
Extra: 013fa7f8bcd6aeb670137934a2f8f155c4b286e5595338a0f5878a6fcb3383ad8e0211000000054b8f5122000000000000000000

1 output(s) for total of 0.815652331000 dcy

stealth address amount amount idx
00: 5f6c1be14ead32c6541bfec7fa78d2a69554f2f38ea843ee9aeab799eea8d870 0.815652331000 1322907 of 0

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": 868146, "vin": [ { "gen": { "height": 868136 } } ], "vout": [ { "amount": 815652331, "target": { "key": "5f6c1be14ead32c6541bfec7fa78d2a69554f2f38ea843ee9aeab799eea8d870" } } ], "extra": [ 1, 63, 167, 248, 188, 214, 174, 182, 112, 19, 121, 52, 162, 248, 241, 85, 196, 178, 134, 229, 89, 83, 56, 160, 245, 135, 138, 111, 203, 51, 131, 173, 142, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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