Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a6131350030be8a6fb1e6c50092c7c6f62df4dd61ca054e2a67109bb4ed004

Tx prefix hash: bfa183502e5284e3e48c965441c48c5999bd16a93cd556dbbad9db857a10c303
Tx public key: 9a312e9e0f32fae2f32e42d55b292228976346fef4e3f2e9a3fbe5ad1ee9549f
Timestamp: 1686450902 Timestamp [UCT]: 2023-06-11 02:35:02 Age [y:d:h:m:s]: 01:258:06:29:05
Block: 779679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445716 RingCT/type: yes/0
Extra: 019a312e9e0f32fae2f32e42d55b292228976346fef4e3f2e9a3fbe5ad1ee9549f02110000000575e3f0e9000000000000000000

1 output(s) for total of 1.601769326000 dcy

stealth address amount amount idx
00: 303db77269b0992ec497839f05b0465de3db6ad19335dc11e6c1e573271a73a4 1.601769326000 1229350 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": 779689, "vin": [ { "gen": { "height": 779679 } } ], "vout": [ { "amount": 1601769326, "target": { "key": "303db77269b0992ec497839f05b0465de3db6ad19335dc11e6c1e573271a73a4" } } ], "extra": [ 1, 154, 49, 46, 158, 15, 50, 250, 226, 243, 46, 66, 213, 91, 41, 34, 40, 151, 99, 70, 254, 244, 227, 242, 233, 163, 251, 229, 173, 30, 233, 84, 159, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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