Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14ece99cb43021654e30f900ecc46426e108f68ebf6fc0ea9c279ead34272aae

Tx prefix hash: 72eaf541b928a6a33d914c6eee66113fa256c7c5a428f031a00c4b7b5eaf11ed
Tx public key: 587288d8f39f9de7b0e81b73c9673c140b8cb8c21df614ef5c3321640fed36aa
Timestamp: 1710187236 Timestamp [UCT]: 2024-03-11 20:00:36 Age [y:d:h:m:s]: 01:079:19:16:51
Block: 976215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318067 RingCT/type: yes/0
Extra: 01587288d8f39f9de7b0e81b73c9673c140b8cb8c21df614ef5c3321640fed36aa02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15b3b83548e41e39050e03d3036e45a67c508154df10cda314ff0ceef7ee3589 0.600000000000 1436206 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": 976225, "vin": [ { "gen": { "height": 976215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15b3b83548e41e39050e03d3036e45a67c508154df10cda314ff0ceef7ee3589" } } ], "extra": [ 1, 88, 114, 136, 216, 243, 159, 157, 231, 176, 232, 27, 115, 201, 103, 60, 20, 11, 140, 184, 194, 29, 246, 20, 239, 92, 51, 33, 100, 15, 237, 54, 170, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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