Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1775332cdab81a4fdf3da3caebb642f52d851fbdded4e5363dd753c5e1ef0d44

Tx prefix hash: 6dd895e23878624b37595d7f92cad9006dbb1df98c0fe9cb9da85b03f9ebe5c1
Tx public key: d454e4b5857d8ef3be80fded097d4d44d21507fea88a910f1eff7e0751a90a03
Timestamp: 1706003427 Timestamp [UCT]: 2024-01-23 09:50:27 Age [y:d:h:m:s]: 02:002:19:16:25
Block: 941488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521608 RingCT/type: yes/0
Extra: 01d454e4b5857d8ef3be80fded097d4d44d21507fea88a910f1eff7e0751a90a0302110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46950018b36e83dbc016e7d3fb5e0a3702b64df91970d23a368de571b9cdba8d 0.600000000000 1399638 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": 941498, "vin": [ { "gen": { "height": 941488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46950018b36e83dbc016e7d3fb5e0a3702b64df91970d23a368de571b9cdba8d" } } ], "extra": [ 1, 212, 84, 228, 181, 133, 125, 142, 243, 190, 128, 253, 237, 9, 125, 77, 68, 210, 21, 7, 254, 168, 138, 145, 15, 30, 255, 126, 7, 81, 169, 10, 3, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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