Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 630107e1693800ddde8bd4150e45caa0495c11942b67a8bdf12c6a700adf856b

Tx prefix hash: 95a2ee6910103cc5390d2d677b4472a025dc8a1dbb16a9d4f4e0f4cbbd1283c4
Tx public key: e3498d0cb174d124cf758136f50626c8b01c944660e23a719d9b8744aeb23965
Timestamp: 1722774121 Timestamp [UCT]: 2024-08-04 12:22:01 Age [y:d:h:m:s]: 00:248:22:34:36
Block: 1080546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177824 RingCT/type: yes/0
Extra: 01e3498d0cb174d124cf758136f50626c8b01c944660e23a719d9b8744aeb23965021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dbe1813b2d1af679a92646929e8cb8ad80f1d4399d90f2e7eb09d37311a4bbd 0.600000000000 1553951 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": 1080556, "vin": [ { "gen": { "height": 1080546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dbe1813b2d1af679a92646929e8cb8ad80f1d4399d90f2e7eb09d37311a4bbd" } } ], "extra": [ 1, 227, 73, 141, 12, 177, 116, 209, 36, 207, 117, 129, 54, 245, 6, 38, 200, 176, 28, 148, 70, 96, 226, 58, 113, 157, 155, 135, 68, 174, 178, 57, 101, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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