Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4feaf0aba7580e31ea56e87fb53c507240d375bebcf0ff4d1d721f48fcb2ed0

Tx prefix hash: 9086fa02c38a5bcaf146ac98b18eaf597f58ace9b7edec2d0e00b36c404f2f8d
Tx public key: 5b48ffde9f0456c4c05412eb4ebc82ff434dcc9dd5631548f6dad6015fa1f3e6
Timestamp: 1712564744 Timestamp [UCT]: 2024-04-08 08:25:44 Age [y:d:h:m:s]: 01:049:10:17:36
Block: 995887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296338 RingCT/type: yes/0
Extra: 015b48ffde9f0456c4c05412eb4ebc82ff434dcc9dd5631548f6dad6015fa1f3e602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d931c8b1ce176d40034bd3e09de2e43d12d7f0666fccd0d7ba567eeab80942c8 0.600000000000 1456301 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": 995897, "vin": [ { "gen": { "height": 995887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d931c8b1ce176d40034bd3e09de2e43d12d7f0666fccd0d7ba567eeab80942c8" } } ], "extra": [ 1, 91, 72, 255, 222, 159, 4, 86, 196, 192, 84, 18, 235, 78, 188, 130, 255, 67, 77, 204, 157, 213, 99, 21, 72, 246, 218, 214, 1, 95, 161, 243, 230, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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