Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7319e03d0cb214358b4098b40c7fd33d655147e6f5d9441c013fd4d8bba723d0

Tx prefix hash: 2081c26e053fa0990ffefec7eeb71f2a1225e2ec2f228eff156ac5952deb185a
Tx public key: 88dafd4197ca760806610c36749f35383a5da4cc5fbe5a5e21e5af6f9896c77f
Timestamp: 1714810523 Timestamp [UCT]: 2024-05-04 08:15:23 Age [y:d:h:m:s]: 00:331:13:42:01
Block: 1014538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237011 RingCT/type: yes/0
Extra: 0188dafd4197ca760806610c36749f35383a5da4cc5fbe5a5e21e5af6f9896c77f02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11e4b3d873e33e7dd21a0c77da1e23a8e50d370b0db603e4d4db2800b5ffc61c 0.600000000000 1477655 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": 1014548, "vin": [ { "gen": { "height": 1014538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11e4b3d873e33e7dd21a0c77da1e23a8e50d370b0db603e4d4db2800b5ffc61c" } } ], "extra": [ 1, 136, 218, 253, 65, 151, 202, 118, 8, 6, 97, 12, 54, 116, 159, 53, 56, 58, 93, 164, 204, 95, 190, 90, 94, 33, 229, 175, 111, 152, 150, 199, 127, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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