Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed359e4897b88893a0056ec5d134d726be79e2e3d019847e4309554fc4f15040

Tx prefix hash: edee4bbce148f7e946f76aec5e228568c6d6f69551bb5924ef260af942de922f
Tx public key: ff80234363399c4926249b724277cfe5e4cc630a9fedf2f79d7f7d062f78d84f
Timestamp: 1675033573 Timestamp [UCT]: 2023-01-29 23:06:13 Age [y:d:h:m:s]: 02:079:15:36:25
Block: 685652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 578556 RingCT/type: yes/0
Extra: 01ff80234363399c4926249b724277cfe5e4cc630a9fedf2f79d7f7d062f78d84f02110000000d835e4d22000000000000000000

1 output(s) for total of 3.282088071000 dcy

stealth address amount amount idx
00: c215d06dc2d522704379fb286d8eb2ebba606c407fe0108b16d6dae16a4264d5 3.282088071000 1128015 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": 685662, "vin": [ { "gen": { "height": 685652 } } ], "vout": [ { "amount": 3282088071, "target": { "key": "c215d06dc2d522704379fb286d8eb2ebba606c407fe0108b16d6dae16a4264d5" } } ], "extra": [ 1, 255, 128, 35, 67, 99, 57, 156, 73, 38, 36, 155, 114, 66, 119, 207, 229, 228, 204, 99, 10, 159, 237, 242, 247, 157, 127, 125, 6, 47, 120, 216, 79, 2, 17, 0, 0, 0, 13, 131, 94, 77, 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