Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63f4d5c8b75f4f60544967c66c65d3134da49a02913f1ad21185b1be2ea8d7f4

Tx prefix hash: 2715e9845af098add3767b40707611aed82b74885d0f55049916c84d7056f684
Tx public key: 1e2997edf45e1135fc5e56e6bfe52fe81cca8cd7bf3f19e83e35754ea9050b19
Timestamp: 1706791397 Timestamp [UCT]: 2024-02-01 12:43:17 Age [y:d:h:m:s]: 01:065:22:35:35
Block: 948036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308193 RingCT/type: yes/0
Extra: 011e2997edf45e1135fc5e56e6bfe52fe81cca8cd7bf3f19e83e35754ea9050b1902110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3b7948c4775db25ee1df6d0d3c5f2d0229752d18babafb4ef790b9f4ff3d00a 0.600000000000 1406406 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": 948046, "vin": [ { "gen": { "height": 948036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3b7948c4775db25ee1df6d0d3c5f2d0229752d18babafb4ef790b9f4ff3d00a" } } ], "extra": [ 1, 30, 41, 151, 237, 244, 94, 17, 53, 252, 94, 86, 230, 191, 229, 47, 232, 28, 202, 140, 215, 191, 63, 25, 232, 62, 53, 117, 78, 169, 5, 11, 25, 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