Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a834e402b0ea8acad25e3e69d808777edf50ee9ac85260f41453a527b1ceff16

Tx prefix hash: 171e6a1b74d6fcdc6431d00b04718b326b044e3e3eab21c0e8c6922d5d04e902
Tx public key: 3e23b4546834f285aec6eb2f53679f8b6a5b7c3d6893a3e6e6516462e8cf15ea
Timestamp: 1706717874 Timestamp [UCT]: 2024-01-31 16:17:54 Age [y:d:h:m:s]: 01:306:18:17:46
Block: 947418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478076 RingCT/type: yes/0
Extra: 013e23b4546834f285aec6eb2f53679f8b6a5b7c3d6893a3e6e6516462e8cf15ea0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a09467a73a2f21d73d2496c0de74e763fc6269ab1fdab3d7c428a514e7f62510 0.600000000000 1405766 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": 947428, "vin": [ { "gen": { "height": 947418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a09467a73a2f21d73d2496c0de74e763fc6269ab1fdab3d7c428a514e7f62510" } } ], "extra": [ 1, 62, 35, 180, 84, 104, 52, 242, 133, 174, 198, 235, 47, 83, 103, 159, 139, 106, 91, 124, 61, 104, 147, 163, 230, 230, 81, 100, 98, 232, 207, 21, 234, 2, 17, 0, 0, 0, 5, 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