Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18a4abbe347ec73bae435d0f6eeaf3fe2e4e15e63055735bb792115674ec4d6

Tx prefix hash: 5dc08662deb11006ef068f5de185e8809ab8c3c4e379cd9ea227695d479e88df
Tx public key: 1c150fc43a63a6040860a645ce3df1c1b952adb6c391e5ac057a6441f2f8c292
Timestamp: 1723546713 Timestamp [UCT]: 2024-08-13 10:58:33 Age [y:d:h:m:s]: 00:248:18:26:37
Block: 1086962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177678 RingCT/type: yes/0
Extra: 011c150fc43a63a6040860a645ce3df1c1b952adb6c391e5ac057a6441f2f8c29202110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7c10634fb1f302a3ede8731c0cc979405220895e5864d7d5aa6d2d7a612107e 0.600000000000 1561561 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": 1086972, "vin": [ { "gen": { "height": 1086962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7c10634fb1f302a3ede8731c0cc979405220895e5864d7d5aa6d2d7a612107e" } } ], "extra": [ 1, 28, 21, 15, 196, 58, 99, 166, 4, 8, 96, 166, 69, 206, 61, 241, 193, 185, 82, 173, 182, 195, 145, 229, 172, 5, 122, 100, 65, 242, 248, 194, 146, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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