Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a2533a7be6b672c4c52eb88d3cc38500fbb74556e28d9b3cb5845b3b04d90a1

Tx prefix hash: 3f39246f18e0316ecc8e360bc73ea5665837222d25c0eb86bcaed10808f6e3dd
Tx public key: 2ccdc5d3cd1b3746ace9f9e52c9061c4ebbd79f18d3987d0da85ba273523e236
Timestamp: 1684174032 Timestamp [UCT]: 2023-05-15 18:07:12 Age [y:d:h:m:s]: 01:324:15:49:42
Block: 760790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493263 RingCT/type: yes/0
Extra: 012ccdc5d3cd1b3746ace9f9e52c9061c4ebbd79f18d3987d0da85ba273523e23602110000000233af99f4000000000000000000

1 output(s) for total of 1.850065474000 dcy

stealth address amount amount idx
00: 470100ee0da902e77052fc576dda6eab6c312b4e1538e2401e58ac8467ee9b0d 1.850065474000 1209425 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": 760800, "vin": [ { "gen": { "height": 760790 } } ], "vout": [ { "amount": 1850065474, "target": { "key": "470100ee0da902e77052fc576dda6eab6c312b4e1538e2401e58ac8467ee9b0d" } } ], "extra": [ 1, 44, 205, 197, 211, 205, 27, 55, 70, 172, 233, 249, 229, 44, 144, 97, 196, 235, 189, 121, 241, 141, 57, 135, 208, 218, 133, 186, 39, 53, 35, 226, 54, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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