Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2105d4d766240846e69f6630dc9c65c0d4c9581fc8f54223e46aeae659d34281

Tx prefix hash: 4c6b38e02f76e61e62480e6d98a870e52559215b356c65ca17e49beda25878a0
Tx public key: b69818f6e1f9c93003b4ff54820997a19ac8652add3f2704f2cd760cbe58a6cb
Timestamp: 1698591180 Timestamp [UCT]: 2023-10-29 14:53:00 Age [y:d:h:m:s]: 01:181:22:28:58
Block: 880279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391046 RingCT/type: yes/0
Extra: 01b69818f6e1f9c93003b4ff54820997a19ac8652add3f2704f2cd760cbe58a6cb02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.743481667000 dcy

stealth address amount amount idx
00: 32e2636adebaee1af10858707dec3d2755b70b9874f15b8c3b0537c5d7b1bb14 0.743481667000 1335825 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": 880289, "vin": [ { "gen": { "height": 880279 } } ], "vout": [ { "amount": 743481667, "target": { "key": "32e2636adebaee1af10858707dec3d2755b70b9874f15b8c3b0537c5d7b1bb14" } } ], "extra": [ 1, 182, 152, 24, 246, 225, 249, 201, 48, 3, 180, 255, 84, 130, 9, 151, 161, 154, 200, 101, 42, 221, 63, 39, 4, 242, 205, 118, 12, 190, 88, 166, 203, 2, 17, 0, 0, 0, 2, 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