Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62e04f97249cf5564273254688940796fe2668d1df688af48a4b949409ca5840

Tx prefix hash: ed088d1180592515201468a88c2eb8bd1fd6b3ed8c0adc54937f22b66b12e344
Tx public key: d65018e74d150c34deda68be60987c9535fd1fb8a2b1c47d0b853d4195318816
Timestamp: 1698063394 Timestamp [UCT]: 2023-10-23 12:16:34 Age [y:d:h:m:s]: 01:033:13:23:37
Block: 875894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285180 RingCT/type: yes/0
Extra: 01d65018e74d150c34deda68be60987c9535fd1fb8a2b1c47d0b853d419531881602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.768775609000 dcy

stealth address amount amount idx
00: 58e7b10c41d7483e67b4b66742d012d7cfcc9cf1fb72687a83779d9278fd0d8a 0.768775609000 1331188 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": 875904, "vin": [ { "gen": { "height": 875894 } } ], "vout": [ { "amount": 768775609, "target": { "key": "58e7b10c41d7483e67b4b66742d012d7cfcc9cf1fb72687a83779d9278fd0d8a" } } ], "extra": [ 1, 214, 80, 24, 231, 77, 21, 12, 52, 222, 218, 104, 190, 96, 152, 124, 149, 53, 253, 31, 184, 162, 177, 196, 125, 11, 133, 61, 65, 149, 49, 136, 22, 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